home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93b.txt
/
000130_icon-group-sender _Wed Jun 9 13:56:54 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-06-16
|
1KB
Received: from owl.CS.Arizona.EDU by cheltenham.CS.Arizona.EDU; Wed, 9 Jun 1993 12:43:44 MST
Received: by owl.cs.arizona.edu; Wed, 9 Jun 1993 12:43:42 MST
Date: Wed, 9 Jun 93 13:56:54 EDT
From: Paul_Abrahams@MTS.cc.Wayne.edu
To: icon-group@cs.arizona.edu
Message-Id: <677397@MTS.cc.Wayne.edu>
Subject: Initialization files for Icon programs
Status: RO
Errors-To: icon-group-errors@cs.arizona.edu
Here's a problem I ran into recently, which probably occurs with many
Icon programs. My program, on starting, reads in certain initialization
files. I want to keep those files in the same directory as the program's
icode file, i.e., the .icx file (or, for Unix, the "p" file for program
p.icn). However, I don't want to require the program to know the full
path name of the initialization files, since that might change according
to where the program and its files have been installed.
So here's the problem: how, within the program, can I determine the full
path name of the icode file so that I can construct the full path name of
the initialization files? I'm interested in the solution to this problem
for three cases: DOS, OS/2, and Unix. Is it much easier in some systems
than in others?
Thanks.
Paul Abrahams
Reply-To: abrahams@acm.org